> Strange alpha channel bug
> (assumed_gamma affects the transparency of shadowed areas)
> http://news.povray.org/3c1168c5$1@news.povray.org

Logged as job000210.

> problem with transparent image_maps
> (Objects with transparent image_maps have "non-transparent" shadows)
> http://news.povray.org/3c24d1b3@news.povray.org (cancelled)
> http://news.povray.org/eGSwuBAritK8EwLH@econym.demon.co.uk

Logged as job000211.

> CSG difference with text
> (Text objects appear to be very slightly tilted)
> http://news.povray.org/3c304eaf@news.povray.org

While very extreme, this is still a coincident surface problem.  Using less
excessive scales will make it go away.

> Julia object bug (Michael McKnight)
> (Visually similar to coincident surfaces)
> http://news.povray.org/3839f08c@news.povray.org

The supplied scene is absolutely unsuitable to say anything, not even detailed
enough to say it is a problem or not.

> Problem with #read
> http://news.povray.org/3c33b55d@news.povray.org

Unless someone cleans up the mess of examples reported as not working as
expected there, it will be assumed to be a user error.  Having the same file
open for read and write is plain nonsense, and the given scenes are incomplete
as the don't close the files at all.  Incomplete scenes are not suitable to
reproduce or confirm bugs.  Sorry!

> crash with some boxes /infinite boxes
> http://news.povray.org/3c375d62$1@news.povray.org

Not a bug.  Using values that are 10e45 in size is not supported nor
documented to be supported.  Future versions of POV-Ray may not allow such
misuse of syntax flexibility.

> #while crash..
> http://news.povray.org/3c38646f@news.povray.org

Assumed to be same as job000205.

> Mapping warp and render window bugs
> (Object lighting is calculated incorrectly when mapping warps are used
> in normals and the object is rotated)
> http://news.povray.org/Xns9190F27EBFE9Bcsbhccse@204.213.191.226

Logged as job000212.

> Black outline in smooth meshes
> (The outline of smooth meshes exhibit black dots or areas (which go away
> with double_illuminate))
> http://news.povray.org/3bf6794e$1@news.povray.org

Afaik double_illuminate is supposed to be used in this case.  The issue of
"inverted normals" is a general problem and not specific to this object as it
has been discussed elsewhere (not sure in which thread).  Reference should be
given to that thread so it can be added to the list of known bugs while this
one can be kept as a special case of a more general problem.

> silly winpov bug
> (Double clicking the title bar on some machines causes "text selection
> not supported")
> http://news.povray.org/3c3b7a3f@news.povray.org

Wasn't this fixed in beta 10 or said to be fixed in beta 11?

> crash inside two #while
> (Possibly specific to Windows 2000)
> http://news.povray.org/3c3f1f29$1@news.povray.org

Same as job000179.

> crash with photons, union, ior, lathe
> (Intel compile only)
> http://news.povray.org/vfra4u0ndv4rf951196881cpt842an4906@4ax.com

Logged as job000213.

> Wrong highlighting in editor
> (function_id)
> http://news.povray.org/jfji3ug1faevn1jk3mlko64sb71ptmmn97%404ax.com

Reported as fixing in next beta afaik.

> max_trace_level affects radiosity recursion_limit
> ((beta 10) max_trace_level sets an upper bound on recursion_limit)
> http://news.povray.org/3BE40295.6C3D54DE@engineer.com

Has not been confirmed.  No example provided either.

> Media visible container line in front of object
> (a visible whitish line appears at the edge of a transparent container
> box for media)
> http://news.povray.org/3bf45a3d@news.povray.org

The example scene is too complex and it hasn't been confirmed either.

> [win gui] line with error highlighted but render finished succesfully
> http://news.povray.org/va2tvt4tuitd67ik5t9ps334sbg6205bt3@4ax.com

Isn't the highlighted error simply a text selection?  Either way, the bug has
not been confirmed.

> transform syntax
> (transform {test_trans} sometimes requires {} and sometimes doesn't)
> http://news.povray.org/3C09EE1B.A38DC91A@gmx.de

Logged as job000214.

> media & fog bug?
> http://news.povray.org/3c1379e0$1@news.povray.org

This is not confirmed and there is even disagreement noted in the thread if
this is a bug at all!

> Re: Mosaic... some clarifications
> (#local A2=P(1,2,3).hf; fails)
> http://news.povray.org/9n9j1uo0mdlrs4i5toupujr0pqrj4vvb8d@4ax.com

This is not a bug at all and not documented to work the way it is used.
".hf" is only supported to help port MegaPOV functions more easily.  It will
be removed completely in future versions, that is why it is simply marked as
experimental.

> Re: hollow in light groups
> http://news.povray.org/3c21172d$1@news.povray.org
>
> Bug with transform syntax
> http://news.povray.org/chrishuff-5FC1B7.19310427122001@netplex.aussie.org

Same as job000214.

> another crash with max_intersections
> http://news.povray.org/j8fo2u8mbo97gi3as0udmab7t9ttap2iom@4ax.com

Note that setting "max_intersection 0" is simply brain-dead.

> blob casting incorrect shadows on itself
> http://news.povray.org/Xns919C1CAA3E23Egerovandordatanethu@204.213.191.226

Same as the other blob bugs.

> <1, 0, 0> + 1*t
> (Vector arithmetic using "t" behaves oddly)
> http://news.povray.org/3c4bb31d$1@news.povray.org

Works as designed - not a bug.  Adding 3D and 4D vectors the promotion of the
vectors is undefined, adding 4D and 4D vectors or 3D and 3D vectors is the
correct way to do it.  Future versions of POV-Ray may not allow such misuse of
syntax flexibility.

> Initialisation of a 4-vector array
> (Vector arithmetic using "t" behaves oddly)
> http://news.povray.org/3c4fe83b@news.povray.org

Works as designed - not a bug.  The array is created with 3D vectors and later
an attempt is made for a 4D vector into it.  Future versions of POV-Ray may
not allow such misuse of syntax flexibility.

> Severe Lightbug, probably concerned with Macros... (long post)
> (Objects with doubly rotated warp turbulence normals appear to
> illuminated incorrectly)
> http://news.povray.org/3C4ABED3.F038E200@gmx.de

Assumed to be same as job000212 until someone can demonstrate it is not the
same.

> Heightfield bug (most probably an inverted normals problem)
> http://news.povray.org/3c4ca8ff@news.povray.org

See note somewhere above regarding inverted normals.

> rare conic prism bug
> (strange behaviour of illumination/texture of conic prisms)
> http://news.povray.org/3C51212E.9090707@irrwerk.de

Not properly confirmed.  Just being able to reproduce the exact behavior is
not enough.  At least a tiny bit of experimentation should be done to be able
to say it is a bug and not a precision problem.

> macros without commas takes parameter wrongly
> http://news.povray.org/bp925u4upa1gl9kih2pikg4qusf0lr03kg@4ax.com

Works as designed - not a bug.  Commas between macro parameters are required.
Future versions of POV-Ray may not allow such misuse of syntax flexibility.

> Shadow faults
> http://news.povray.org/3c53b38e@news.povray.org

The simplified version works correctly. The long version is to complex. Not
properly confirmed.


    Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message